home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 4
/
Aminet 4 - November 1994.iso
/
aminet
/
comm
/
uucp
/
wcnews_1_0_30.lha
/
notebook
/
dirs.man
< prev
next >
Wrap
Text File
|
1994-01-04
|
4KB
|
133 lines
1mDirectory22m 1mLayout22m 1mand22m 1mPATH22m 1min22m 1mC22m 1mNews22m
4mHenry24m 4mSpencer24m
Dept. of Zoology
University of Toronto
1mIntro22m
C News is constrained by historical compatibility with B
News, but we also want to provide more flexibility for local
news administrators. Accordingly, our directory organiza
tion is a little different from that of B News. We also
make a lot of use of subordinate programs rather than lump
ing everything into a few giant lumps, and this means we
need a notion of search paths.
See also ``Configuration Mechanisms in C News'', which talks
about how to alter the defaults for these paths and such.
1mDirectory22m 1morganization22m
We retain the notion that a single directory (usually
/usr/spool/news) is the top of the newsarticle database.
We also use subdirectories of this directory, using names
including `.' to ensure that they cannot collide with news
group names, to hold incoming batches and outgoing batch
control files. One can debate whether this is the right
place for these activities, but in practice /usr/spool/news
tends to be where people want to put potentiallybig traf
fichandling directories, and it's not worth providing for
separate variation of the location.
We do split the former /usr/lib/news into two, however. We
reserve /usr/lib/news itself for control files that are log
ically part of the database. (It would make sense to put
those under some subdirectory of /usr/spool/news, but that
would break a lot of programs that think these files live in
/usr/lib/news.) The programsthose which don't need to be
directly executable by users or 4muucp24mlive in
/usr/lib/newsbin. Actually, they usually live in subdirec
tories thereof, with each significant subsystem having its
own subdirectory to keep the individual directories manage
able in complexity. There are occasional generalpurpose
utilities at the top level; there aren't enough of them to
be worth a separate directory.
1mPATH22m
In general, things are organized to permit sharing of
/usr/lib/newsbin among multiple databases. It doesn't make
sense to share /usr/lib/news among multiple databases, as
much of the stuff that lives there is logically part of the
database.
There is a possibility that an individual database will want
to override specific decisions made by the programs, i.e.
12 Dec 1988
2
will want its own version of some programs. Accordingly,
provision is made for a `bin' directory under /usr/lib/news.
News software should set its PATH to something on the order
of
/usr/lib/news/bin:/usr/lib/newsbin/xxx:/usr/lib/newsbin:/bin:/usr/bin
(See the ``Configuration Mechanisms'' document for how this
should 4mactually24m be written, to facilitate configuration
changes and local customization.) That is, first look in
the database's bin directory for overrides, then in some
subdirectory of /usr/lib/newsbin for the subsystem's pro
grams, then in newsbin itself for newswide utilities, then
in the standard system directories for standard Unix utili
ties.
12 Dec 1988